~4Dgifts/toolbox/src/exampleCode/games/IndiZone README
INDIZONE SOURCE CODE
`!' indicates new or updated as of version 4.2
oort, and sw contain the full source code for three submissions to the
Indigo Games Contest of June, 1993. blix, gold, tagh, contain the full
source code for four submissions to the IndiZone II Games Contest of
January, 1994. These submissions are:
oort vehicular combat on an asteroid
2/25/96: unfortunately we have
had to remove oort from the DT
as it is no longer compatible
with Performer 2.0. its author
has not the time to upgrade it
to work under PF 2.0 -- it anyone
out there would like to do this,
please let the janitor know.
sw combat in space
blix the mighty mouse hero of indizone
cycles solo or multiplayer (network) motorcycle game
gold synthetic fish bowl simulation
tagh variation on the children's game of tag
! vroom slot car racing in the future
In order to compile these games, you need to have 5.* loaded on your system,
and also the following software on your machine:
oort Performer, Motif, libimage, Audio, C
sw Inventor, GLX, Motif, Audio, C
blix libimage, Audio, libfm, GL, C
cycles libfm, GL, Audio
gold Audio, GL
tagh GL
vroom OpenGL, -lfpe -lGLw -lXm -lXt -lGL -lX11 -lPW -laudiofile -laudio -lmalloc -lm
cycles, oort, sw, tagh, and provide excellent examples of how to
use networking in a game.
If your system is not running some flavor of 5.*, you will not be
able to compile these programs.
Here are explicit instructions for how to start each of the games.
blix requires no specific options to start.
cycles requires no specific options to start. however:
cycles [ -i ifaddr ] [ -t ttl ]
COMMAND LINE OPTIONS
See also the TCP/IP User's Guide and mrouted(1M).
-i ifaddr select the outgoing interface address (if you
have multiple network interfaces)
-t ttl select the time to live of multicast packets
(default 1).
gold requires no specific options to start. however:
usage: gold [-bceflmv]
-b don't display the bubbles visible by default
-c don't show the controls visible by default
-e prevent sexual reproduction from taking place
-f keep fish from eating each other (mightn't work--old debug cruft)
-l don't display the landscape visible by default
-m enable's malloc debugging
-v open as 640x480 NTSC video-sized window w/large cursor
oort requires no specific options to start.
NOTE the oort.sh script--unless you have the IndiZone
games data files already loaded underneath
/usr/demos/IndiZone, you will need to explicitly define
the OORT_DIR environment variable to point to the relative
position of the oort data directory. The oort.sh script
does this before invoking oort.
sw for sw (Spacewar) to run, you MUST copy the Spacewar.ad
app-defaults file to /usr/lib/X11/app-defaults/Spacewar.
This is necessary because the explosionDirectory and
soundDirectory resources must point to the sw directory
which, initially is specified to simply be ".".
sw requires that the server be started before sw can be
run. You can start the server on a single machine for a
game by typing
sws &
All other players will type that machine's name for the
server.
sw itself requires a number of options. First, it requires
that you you type in -n callsign, followed by -s server and
a team color, either r (red), g (green), b (blue) or
p (purple).
As an example, if sws was running on the machine "dessert",
a player called Tom playing on the blue team would start sw
like this:
sw -n Tom -s dessert b
tagh To use Tagh from a shell or launch window enter:
tagh hostname
where "hostname" is the name of a machine on the network.
That machine will act as a server for the game. Up to
three players can participate in a game. For each game,
there should be only one host. For example, if users on
machines "foo" "bar" and "ding" want to play a game
together, they might all type:
tagh foo
Documentation
Reference
Subdirectories
OR, ...